Maintaining system security

ABSTRACT

Maintaining system security by receiving metadata associated with at least a part of one data file from a metadata storage unit, generating a priority for the at least a part of one data file according to the metadata, and conducting a scan of the part of the data file. The metadata includes one or more virus indicators.

BACKGROUND

The disclosure relates generally to maintaining the data processingsystem security and the integrity of data in a big data storage system.The disclosure relates particularly to maintaining system security anddata integrity by scanning for malicious code and data.

Current multi-tenant systems, such as health care, retail,telecommunications, and financial services systems, may have multiplevendors, customers, and service organizations connected to a singlelogical data processing system. The logical data processing system maybe cloud-based or local and may receive continuous streams of data aswell as bulk data batches, accumulating to gigabyte and terabytes ofdata in a data store.

Incoming data must be scanned for viruses, malware and other maliciousdata to maintain the security of the system and its users. Existing datamust be rescanned as virus definitions are updated as new zero-dayexploits are identified. An intrusion prevention system (IPS) is used tomonitor incoming data. The IPS may be inline, monitoring live data as itis streamed from external sources to the data lake for storage, or maybe out-of-band, processing copies of the data passed to the IPS.Incoming data may also include redundant data which increases theworkload of the IPS by requiring scanning of duplicate content.

The scanning activities of the IPS must be carried out withoutdisruption of customer access to the data and without disrupting thecontinuous streams of incoming data. The streams must be landed in thesystem without disruption to continue normal operations, reduceingress/egress costs, reduce or eliminate any waste of system resources,and maintain full access to system services to users and other parts ofthe system platform.

SUMMARY

The following presents a summary to provide a basic understanding of oneor more embodiments of the disclosure. This summary is not intended toidentify key or critical elements or delineate any scope of theparticular embodiments or any scope of the claims. Its sole purpose isto present concepts in a simplified form as a prelude to the moredetailed description that is presented later. In one or more embodimentsdescribed herein, devices, systems, computer-implemented methods,apparatuses and/or computer program products enable prioritizing andscanning data files for malicious code prior to allowing users to accessthe data.

In one aspect, the invention includes methods, systems and computerreadable media associated with maintaining system security bycontinuously monitoring data files as they are streamed or received inbulk, before the files are processed or otherwise accessed by users. Inthis aspect, the systems, methods and computer program products proceedby receiving metadata associated with at least a part of one data filefrom a metadata storage unit, generating a priority for the at least apart of one data file according to the metadata, and conducting a scanof the part of the data file. The metadata includes one or more virusindicators. Once received, the data is provided to users withoutdisruption.

In one aspect, the invention includes methods, systems and computerreadable media associated with maintaining system security as virusdefinitions change over time. In this aspect, the systems, methods andcomputer program products proceed by receiving an updated virusdefinition, obtaining metadata associated with at least one data filefrom a metadata storage unit, generating a priority for the at least onedata file according to the metadata and updated virus definition,selecting a data file according to the generated priority, conducting ascan of the data file, updating the metadata of the data file accordingto the scan, and providing the data file for further processing.

In one aspect, the invention includes methods, systems and computerreadable media associated with maintaining system security including theadditional advantage of providing a user, or automated receiving system,the common vulnerability and exposures scoring for each scanned file.The user or receiving system then determines if the scanned file shouldbe loaded into a data processing system for further processing and use.The inventions of this aspect proceed by obtaining metadata associatedwith at least one data file from a metadata storage unit, generating apriority for the at least one data file according to the metadata,selecting a data file according to the priority, conducting a scan ofthe data file, determining a common vulnerabilities and exposures scorefor the data file, updating the metadata of the data file according tothe scan, and providing the score to a system user for evaluation.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some embodiments of the presentdisclosure in the accompanying drawings, the above and other objects,features and advantages of the present disclosure will become moreapparent, wherein the same reference generally refers to the samecomponents in the embodiments of the present disclosure.

FIG. 1 provides a schematic illustration of a system, according to anembodiment of the invention.

FIG. 2 provides a flowchart depicting an operational sequence, accordingto an embodiment of the invention.

FIG. 3 depicts a cloud computing environment, according to an embodimentof the invention.

FIG. 4 depicts abstraction model layers, according to an embodiment ofthe invention.

DETAILED DESCRIPTION

Some embodiments will be described in more detail with reference to theaccompanying drawings, in which the embodiments of the presentdisclosure have been illustrated. However, the present disclosure can beimplemented in various manners, and thus should not be construed to belimited to the embodiments disclosed herein.

In an embodiment, one or more components of the system can employhardware and/or software to solve problems that are highly technical innature (e.g., prioritizing data files according to metadata and scanningprioritized files, etc.). These solutions are not abstract and cannot beperformed as a set of mental acts by a human due to the processingcapabilities needed to facilitate code scanning and remediation, forexample. Further, some of the processes performed may be performed by aspecialized computer for carrying out defined tasks related to memoryoperations. For example, a specialized computer can be employed to carryout tasks related to code scanning and remediation or the like.

Distributed big data processing systems face unique system securityissues. These systems receive and distribute very large data files,measured in gigabytes and terabytes. The received data originates from ahost of sources, some more reliable than others, and some of which maynot check or ensure that the provided data is free of viruses, malware,and other embedded issues with data. System users require uninterruptedaccess to system data across a distributed environment, where stoppingservices or data access to review or remediate data issues is not aworkable option. System users may download blocks of data for furtherprocessing and use. An indication of the security profile of the dataassists users in determining which blocks are safe to add to a dataprocessing system for use. Such systems may also receive duplicate filesfrom a single source or from multiple sources. Processing duplicaterecords for security issues wastes scarce system resources.

In an embodiment, the system includes a data store for storage of large(gigabyte and terabyte sized) files. The system also includes a metadatastorage unit which holds one or more metadata tables. The metadatastorage unit may be local, or cloud based. The tables include metadatarecords for the large files held in the data store. In this embodiment,the tables hold metadata fields including some or all of: data relatingto file identification, file processing status—is the file available fordownstream uses etc., file processed time—a record of the last time thedata was processed by the method, a common vulnerabilities and exposures(CVE) score for the file, viruses identified within the file, detailedvirus description data, file format information, and data relating toany downstream processing needs of the file. Different file formats aremore closely correlated with data borne issues. Files associated withdownstream processing, as opposed to long term storage, require moreimmediate attention and scanning.

The disclosed inventions are applicable to single or multipleapplication systems fixedly deployed on a single server or distributedacross multiple cloud tenancies. The inventions are applicable to nearreal time data processing of streaming data as well as batch and bulkdata processing.

In some embodiments, the metadata also includes checksum data associatedwith the data files. For bulk or batch data files received out-of-band,the method computes a checksum, such as the hash value (SHA256), for thefile. Even minor changes to the file will result in a different checksumvalue, indicating that the file has been altered. The checksum is storedas metadata associated with the file. In some embodiments, the file maybe provided with a checksum value. In these embodiments, the methodcompares the calculated checksum with the provided value to determine ifchanges have been made to the file. The checksum may use a checksumtechnique such as SHA256, MD5, or any other method of calculating achecksum using the data file byte representation.

In an embodiment, the method calculates checksum values for streamliningdata files as well as bulk files received out-of-band. For streamingdata, the method continuously calculates checksum values in parallel tothe streaming data landing in the data store of the system. The methodstores the checksum values calculated during streaming as metadata in alookup table. After the data file has completely landed, the finalchecksum value for the file is stored in the metadata storage unit inassociation with the streamed file. In an embodiment, the methodsubdivides the data file into parts as blocks or segments of the file.In this embodiment, the method computes a checksum for each part of thedata file. As each part is completely received, the checksum for eachpart of the data file is stored as metadata associated with that part ofthe file. In an embodiment, the parts overlap to ensure that viruses arenot split between adjacent blocks and overlooked. Segments can be paddedsuch that each segment includes a portion of the previous segment, forexample, each 100-megabyte segment can be padded to include the last 100kilobytes of the previous segment. In one embodiment, 100-megabytesegments are padded+/−500 kilobytes, to ensure that there are no gaps inthe segment scanning due to segmenting the data file. In thisembodiment, the segments would range from 0-1.5 MB, 1-2.5 MB, 2-3.5 MB .. . thereby reducing the likelihood that a portion of malicious codewould evade detection by being split between two adjacent segments.

In an embodiment, the method compares the checksum values with storedmetadata values associated with existing data files and segments. Thecomparison identifies duplicates of the current batch or streamingfile/segment. The method compares continuously calculated checksums asfiles are streamed to the data store, identifying potentially similar oridentical files. In this embodiment, the method uses the final checksumto validate any potentially identical files as actually identical.

In an embodiment, in response to matching a checksum in the metadata,the method triggers a cleansing routine for the file or file segmentbased upon the CVE score and virus details of the matched file/segment.In this embodiment, the matched metadata is associated with a filehaving known viruses. In this embodiment, the method cleans the file orsegment and updates the metadata indicating that the cleaning hasoccurred. Cleaning the files can include removing known malicious codeportions associated with a detected virus from the file, or restoringthe file using a backup copy of the file. The cleaned file is added tolist for prioritization. In this embodiment, the method calculates a newchecksum for the cleaned file and adds the new checksum to the metadata.

In an embodiment, the method checks the metadata storage unit todetermine if new data store batch files have been loaded, or todetermine if new streaming data files are loading. In this embodiment,the method checks the metadata associated with any new files. The methodthen continuously monitors the metadata storage unit for indications ofnew data files. In an embodiment, the method and systems of theinvention rest when no new files or virus definitions are detected.

In an embodiment, the method obtains the metadata for any recentlyloaded or currently streaming files. The method generates a prioritizedlisting of new data files using the metadata. The files are prioritizedin view of virus indicators, or the likelihood of a file having malware.The method correlates the metadata of all new files to generate theprioritized list. The method considers checksum values relative topreviously scanned files in terms of previously found viruses. Themethod also considers the virus definition used in any previous scan ofa file or duplicate, and whether the virus definition is up to date.Scans made using now out of date virus definition scans rate a higherpriority for a new scan. Data files needing downstream processing rate ahigher priority than files lacking such needs. Files having a checksumdeviation compared to either a provided checksum, or a previous scanchecksum, rate a higher priority for a new scan. In this embodiment, themethod considers the metadata of the set of new and existing files inview of any changes to the virus definitions. The method ranks the setof data files and prioritizes the files from highest (most in need of ascan) to lowest, (least in need of a scan). In this embodiment, themethod reviews new unprocessed files—those with no matching fileidentification or file checksum, rates these files as high priority andcreates a new metadata listing in the metadata storage unit for thefiles. The method also blocks user access to unprocessed files at leastuntil after scanning has been completed for the files. In thisembodiment, the method considers duplicate files having the same fileidentification and file checksum as an existing file, as low priority.

In an embodiment, the method selects a file from the generatedprioritized list and scans the file for viruses, malware and other databorne issues. In this embodiment, the method selects the data fileaccording to its priority, beginning with the highest priority. Eachfile of the list is scanned in turn according to descending priority. Inthis embodiment, the method selects the highest priority file on thelisting. Files are added to the list together with their priority suchthat a new, high priority file may be scanned before an older filehaving a low priority.

In an embodiment, the method scans the files for viruses utilizing thedetailed current virus definitions. In this embodiment, the methoddetermines a CVE score for each file as well as a listing of virusesfound for each file. The time of the scan, virus definition used,viruses found, number of viruses found, file checksum, file format anddownstream processing needs associated with the file are all updated asthe metadata for the file in the metadata storage unit.

In an embodiment, files are subdivided into blocks or segments tofacilitate faster scanning and to optimize file storage. In thisembodiment, the method determines and stores metadata for each segmentas well as the overall file. In this embodiment, the method includesrelated segment data as part of the metadata. Scanning one segment of agroup of related segments triggers scans of the nearby related segments.In this embodiment, the scans of related segments overlap, increasingthe likelihood of finding viruses and malware. In this embodiment, thefile may be divided, stored and scanned as a series of logically relatedsegments—segment0, segment1, segment2, etc. In an embodiment, the methodscans binary versions of files. In this embodiment, the method maintainsthe files as binary until after the scan is complete and the file issuitable for downstream processing and user access as part of theavailable data store. In this embodiment, the method employs anextract—transform—load, or other data processing agent operation toretrieve the data from the file for use as part of the data store.

In an embodiment, the method evaluates the metadata after scanning afile or segment of a file. The method then provides the file fordownstream processing, provides the file for a virus/malware cleansingroutine, or quarantines the file when cleansing routines areunavailable. In an embodiment, the method provides users access to theCVE score of each file. In this embodiment, the user determines a levelof acceptable risk associated with CVE scores and establishes a CVEscore threshold. Files having a CVE score below the threshold areaccepted into the data processing system of the user for use by dataconsumers. Those with scores above the threshold are refused. In anembodiment, the method uploads files with no viruses found, or withacceptably low CVE scores for downstream use. The method updates themetadata in the metadata storage unit for all scanned files.

As an example:

A Client application connects with a method Platform using TransportLayer Security Mutual Authentication.The Client application starts the upload of healthcare data.The Client has not declared the size of the contents, and the platformmaximum support is for multiple terabyte files.The Platform streams the data into the data store and starts thechecksum using SHA256.The Platform has not yet marked the data ready for download and thedownstream consumers are not yet able to consume the new data.The Platform starts building a checksum for the parts of the file.{Part1: 0-1M, Part 2: 1-2M, Part 3: 2-3M}The Client application finishes uploading the file.The Platform updates the Checksum-01234567A in the metadata supportcolumn along with the calculated checksums for parts of files.Running in parallel, the Platform's virus scanning service checks themetadata column.The metadata contains the following information for the uploaded file:

FILE ID 1-2-1-1 PROCESSED N Checksum 01234567A PROCESSED TIME NULL CVEScore NULL Virus and Virus Details NULL Related Segments NULL(Prior/Next)A method coordinator checks to see if the checksum already exists, if itexists, the invention prioritizes the ones that have no relevant orsimilar checksums.The coordinator, not finding any relevant checksums, extracts the filebased on the time.The coordinator scans the file, and pulls back the results—virus found,virus metadata, and marks the file as processed, with virus content andCVE score.

FILE ID 1-2-1-1 PROCESSED N Checksum 01234567A PROCESSED TIME 2019-02-0107:56:00AM UTC CVE Score CVSS v2.0 Severity and Metrics: Base Score: 5.0MEDIUM Vector: (AV:N/AC:L/Au:N/C:N/I:P/A:N) (V2 legend) Impact Subscore:2.9 Exploitability Subscore: 10.0 Virus Score and Eicar Content RelatedSegments None (Prior/Next)

FIG. 1 provides a schematic illustration of exemplary network resourcesassociated with practicing the disclosed inventions. The inventions maybe practiced in the processors of any of the disclosed elements whichprocess an instruction stream. As shown in the figure, a networkedClient device 110 connects wirelessly to server sub-system 102. Clientdevice 104 connects wirelessly to server sub-system 102 via network 114.Client devices 104 and 110 comprise virus scanning program clients (notshown) together with sufficient computing resource (processor, memory,network communications hardware) to execute the program. As shown inFIG. 1, server sub-system 102 comprises a server computer 150. FIG. 1depicts a block diagram of components of server computer 150 within anetworked computer system 1000, in accordance with an embodiment of thepresent invention. It should be appreciated that FIG. 1 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments can beimplemented. Many modifications to the depicted environment can be made.

Server computer 150 can include processor(s) 154, memory 158, persistentstorage 170, communications unit 152, input/output (I/O) interface(s)156 and communications fabric 140. Communications fabric 140 providescommunications between cache 162, memory 158, persistent storage 170,communications unit 152, and input/output (I/O) interface(s) 156.Communications fabric 140 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 140 can beimplemented with one or more buses.

Memory 158 and persistent storage 170 are computer readable storagemedia. In this embodiment, memory 158 includes random access memory(RAM) 160. In general, memory 158 can include any suitable volatile ornon-volatile computer readable storage media. Cache 162 is a fast memorythat enhances the performance of processor(s) 154 by holding recentlyaccessed data, and data near recently accessed data, from memory 158.

Program instructions and data used to practice embodiments of thepresent invention, e.g., the virus scanning program 175, are stored inpersistent storage 170 for execution and/or access by one or more of therespective processor(s) 154 of server computer 150 via cache 162. Inthis embodiment, persistent storage 170 includes a magnetic hard diskdrive. Alternatively, or in addition to a magnetic hard disk drive,persistent storage 170 can include a solid-state hard drive, asemiconductor storage device, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), a flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 170 may also be removable. Forexample, a removable hard drive may be used for persistent storage 170.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage170.

Communications unit 152, in these examples, provides for communicationswith other data processing systems or devices, including resources ofclient computing devices 104, and 110. In these examples, communicationsunit 152 includes one or more network interface cards. Communicationsunit 152 may provide communications through the use of either or bothphysical and wireless communications links. Software distributionprograms, and other programs and data used for implementation of thepresent invention, may be downloaded to persistent storage 170 of servercomputer 150 through communications unit 152.

I/O interface(s) 156 allows for input and output of data with otherdevices that may be connected to server computer 150. For example, I/Ointerface(s) 156 may provide a connection to external device(s) 190 suchas a keyboard, a keypad, a touch screen, a microphone, a digital camera,and/or some other suitable input device. External device(s) 190 can alsoinclude portable computer readable storage media such as, for example,thumb drives, portable optical or magnetic disks, and memory cards.Software and data used to practice embodiments of the present invention,e.g., virus scanning program 175 on server computer 150, can be storedon such portable computer readable storage media and can be loaded ontopersistent storage 170 via I/O interface(s) 156. I/O interface(s) 156also connect to a display 180.

Display 180 provides a mechanism to display data to a user and may be,for example, a computer monitor. Display 180 can also function as atouch screen, such as a display of a tablet computer.

FIG. 2 provides a flowchart 200, illustrating exemplary activitiesassociated with the practice of the disclosure. After program start, at210 the method of program 175, checks for new batch or streaming filesand/or new virus definitions. Batch files may already be present in thedata store and streaming files may be landing in the data store. Newvirus definitions may be provided to a system Intrusion PreventionSystem by network communications unit 152. At 220, the method checks fornew file metadata in a metadata storage unit of persistent memory 170, asystem storage area network or other system memory. For new fileswithout stored metadata, the method of the program 175 creates a newmetadata record and begins gathering file metadata. The metadata isgathered from the file itself as well as from method activitiesassociated with the file. For new virus definitions, the method checksfor files not yet scanned with the new virus definitions.

At 230, the method of program 175 generates a prioritized listing of allnew files according to their need for virus scanning. The methoddetermines file priority using one or more of calculated file checksumvalues, and a virus correlation indicator from the new files metadata.Higher priorities are assigned to file with a higher urgency forscanning. (Files needing downstream processing access, files with nohistorical metadata, files with checksum issues, etc.).

At 240, the method of program 175 selects the highest priority data filepart from the generated list for scanning. At 250, the method scans thefile using the current virus definitions. At 260, the method updates thefile's metadata including the time and date of the scan, the virusdefinitions used, the number, and the details of any viruses found, thenew CVE score for the file, any related segment information, etc. At270, the method marks the file as clean from known virus at the time ofscan. In this embodiment, the method provides the CVE score todownstream data consumers, data users and administrators. The recipientsof the CVE score determine if the file is sufficiently clean to makeavailable for consumers.

The method passes files containing viruses to file cleansing processes.At 275, the method determines if the file has been cleansed by theprocess. Clean files are passed to step 280. Virus containing fileswhich have not been cleansed are passed to step 290 and are quarantinedfrom data consumer use, and from being added to data consumer access.

At 280, clean files are added to the data store as usable for dataconsumers. After step 280, the method returns to step 210 to check fornew files/virus definitions. When no new files or definitions are found,the method passes to step 215 and determines if all files on thegenerated priority list have been scanned with the current virusdefinitions. The method returns to step 240 and selects the nextprioritized file when all files have not yet been scanned. When allfiles have been scanned, the method returns to step 210 and continues tocheck for new files and virus definitions.

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported, providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 3, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 3 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 4, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 3) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 4 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture-based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and virus scanning program 175.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The invention may be beneficially practiced in any system, single orparallel, which processes an instruction stream. The computer programproduct may include a computer readable storage medium (or media) havingcomputer readable program instructions thereon for causing a processorto carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

References in the specification to “one embodiment”, “an embodiment”,“an example embodiment”, etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to affect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration but are not intended tobe exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A computer implemented method for maintainingdata processing system security, the method comprising: receiving from ametadata storage unit, by one or more computer processors, metadataassociated with at least one part of a data file; generating, by the oneor more computer processors, a priority for the at least one part of thedata file according to the metadata; and conducting, by the one or morecomputer processors, a scan of the data file according to the priority;wherein the metadata comprises one or more vim s indicators.
 2. Thecomputer implemented method according to claim 1, wherein the metadatais associated with a checksum continuously calculated in parallel as thedata file streams into a data store.
 3. The computer implemented methodaccording to claim 1, further comprising: updating, by the one or morecomputer processors, the metadata of the data file according to thescan; and providing, by the one or more computer processors, the datafile for further processing.
 4. The computer implemented methodaccording to claim 1, wherein the priority is generated according to acorrelation of data file metadata.
 5. The computer implemented methodaccording to claim 1, further comprising presenting, by the one or morecomputer processors, the data file to a cleansing routine.
 6. Thecomputer implemented method according to claim 1, further comprising:matching, by the one or more computer processors, a checksum for a partof the data file with a checksum in the metadata storage unit; andtriggering, by the one or more computer processors, a data cleansingroutine in response to the matching.
 7. The computer implemented methodaccording to claim 1, further comprising updating, by the one or morecomputer processors, checksum metadata associated with a part of thedata file.
 8. A computer program product for maintaining systemsecurity, the computer program product comprising one or more computerreadable storage devices and stored program instructions on the one ormore computer readable storage devices, the stored program instructionscomprising: program instructions to receive from a metadata storage unitmetadata associated with at least one data file; program instructions togenerate a priority for the at least one data file according to themetadata; and program instructions to conduct a scan of the data fileaccording to the priority; wherein the metadata comprises one or morevim s indicators.
 9. The computer program product according to claim 8,wherein the metadata is associated with a checksum continuouslycalculated in parallel as the data file streams into a data store. 10.The computer program product according to claim 8, further comprising:program instructions to update the metadata of the data file accordingto the scan; and program instructions to provide the data file forfurther processing.
 11. The computer program product according to claim8, wherein the priority is generated according to a correlation of datafile metadata.
 12. The computer program product according to claim 8,further comprising program instructions to present the data file to acleansing routine.
 13. The computer program product according to claim8, further comprising: program instructions to match a checksum for apart of the data file with a checksum in the metadata storage unit; andprogram instructions to trigger a data cleansing routine in response tomatching the checksum.
 14. The computer program product according toclaim 8, further comprising program instructions to update checksummetadata associated with a part of the data file.
 15. A computer systemfor maintaining system security, the computer system comprising: one ormore computer processors; one or more computer readable storage devices;and stored program instructions on the one or more computer readablestorage devices for execution by the one or more computer processors,the stored program instructions comprising: program instructions toreceive from a metadata storage unit metadata associated with at leastone data file; program instructions to generate a priority for the atleast one data file according to the metadata; and program instructionsto conduct a scan of the data file according to the priority; whereinthe metadata comprises one or more virus indicators.
 16. The computersystem according to claim 15, wherein the metadata is associated with achecksum continuously calculated in parallel as the data file streamsinto a data store.
 17. The computer system according to claim 15,further comprising: program instructions to update the metadata of thedata file according to the scan; and program instructions to provide thedata file for further processing.
 18. The computer system according toclaim 15, wherein the priority is generated according to a correlationof data file metadata.
 19. The computer system according to claim 15,further comprising program instructions to present the data file to acleansing routine.
 20. The computer system according to claim 15,further comprising: program instructions to match, by the one or morecomputer processors, a checksum for a part of the data file with achecksum in the metadata storage unit; and program instructions totrigger a data cleansing routine in response to matching the checksum.21. The computer system according to claim 15, further comprisingprogram instructions to update checksum metadata associated with a partof the data file.
 22. A computer implemented method for maintainingsystem security, the method comprising: receiving, by one or morecomputer processors, an updated virus definition; obtaining, by the oneor more computer processors, metadata associated with at least one datafile from a metadata storage unit; generating, by the one or morecomputer processors, a priority for the at least one data file accordingto the metadata and updated virus definition; selecting, by the one ormore computer processors, a data file according to the priority;conducting, by the one or more computer processors, a scan of the datafile; updating, by the one or more computer processors, the metadata ofthe data file according to the scan; and providing, by the one or morecomputer processors, the data file for further processing.
 23. Thecomputer implemented method according to claim 22, wherein the metadatais associated with a checksum continuously calculated in parallel as thedata file streams into a data store.
 24. A computer implemented methodfor maintaining system security, the method comprising: obtaining, byone or more computer processors, metadata associated with at least onedata file from a metadata storage unit; generating, by the one or morecomputer processors, a priority for the at least one data file accordingto the metadata; selecting, by the one or more computer processors, adata file according to the priority; conducting, by the one or morecomputer processors, a scan of the data file; determining, by the one ormore computer processors, a common vulnerabilities and exposures scorefor the data file; updating, by the one or more computer processors, themetadata of the data file according to the scan; and providing, by theone or more computer processors, the score to a system user forevaluation.
 25. The computer implemented method according to claim 24,wherein the metadata is associated with a checksum continuouslycalculated in parallel as the data file streams into a data store.